Method for performing relay forwarding on integrated access and backhaul links, information acquisition method, node, and storage medium

ABSTRACT

Provided is a method for performing relay forwarding on integrated access and backhaul (IAB) links. The method includes receiving, by a first IAB node, a data packet; and transmitting, by the first IAB node, the data packet to an IAB donor. Further provided are an information acquisition method, an IAB node, an IAB donor node and a storage medium.

CROSS REFERENCE TO RELATED APPLICATIONS

This is a national stage application filed under 37 U.S.C. 371 based onInternational Patent Application No. PCT/CN2019/081545, filed Apr. 4,2019, which claims priority to Chinese patent application No.201810302723.5 filed with the CNIPA on Apr. 5, 2018, disclosures ofwhich are incorporated herein by reference in their entireties.

TECHNICAL FIELD

The present disclosure relates to a field of communications, forexample, to a method for performing relay forwarding on integratedaccess and backhaul links, an information acquisition method, a node,and a storage medium.

BACKGROUND

Usage of a larger available bandwidth, massive Multiple-InputMultiple-Output (MIMO) and multi-beam of 5th-Generation (5G) New Radio(NR) compared to Long Term Evolution (LTE) makes the research andapplication of integrated access and backhaul (IAB) links possible.Through radio backhaul links and relay links, dense NR cell networks canbe deployed more flexibly without increasing transmission network densedeployment accordingly.

In an example of deploying an IAB network, nodes A, B and C are allaccess nodes, a user equipment may connect to the access nodes A, B andC through access links, but only a wired connection between the accessnode A and a core network element exists, and there is no wiredconnection between the access nodes B/C and the core network element. Anaccess node that supports the radio access of the UE and performs radiobackhaul on data is called an IAB node. An access node that provides aradio backhaul function for the IAB node to connect the UE to the corenetwork is called as an IAB donor. Data of the UE may be transmittedamong the access nodes through the radio backhaul links. For example,the access node B may transmit the data received from the UE to theaccess node A through the radio backhaul links, and then the access nodeA transmits the data received from the UE to the core network element.For the downlink, the core network element may transmit a UE data packetto the access node A, and then the access node A transmits the UE datato the access node B through the radio backhaul links, and then theaccess node B transmits the UE data to the UE through the access links.The access links and backhaul links may use same or different carrierfrequencies.

How to perform relay forwarding in the IAB architecture so as tocorrectly transmit and receive the UE's data is the problem to besolved.

SUMMARY

Embodiments of the present disclosure provide a method for performingrelay forwarding on integrated access and backhaul links, an informationacquisition method, a node, and a storage medium to at least solve aproblem of how to relay forwarding in the IAB architecture so as tocorrectly transmit and receive a user equipment (UE)'s data.

The embodiment of the present disclosure provides a method forperforming relay forwarding on integrated access and backhaul (IAB)links, including steps described below.

A first IAB node receives a data packet.

The first IAB node transmits the data packet to an IAB donor.

The embodiment of the present disclosure further provides a method forperforming relay forwarding on integrated access and backhaul (IAB)links, including steps described below.

An IAB donor distribution unit (DU) receives a data packet transmittedby an IAB node.

The IAB donor DU obtains first information, where the first informationincludes at least one of: a source node identifier, a target nodeidentifier, a UE identifier to which the data packet belongs, and abearer identifier to which the data packet belongs, a channel identifierto which the data packet belongs, routing path information, Quality ofService (QoS) related information, general packet radio servicetunneling protocol (GTP) tunnel information, control plane indicationinformation, user plane indication information or protocol typeindication information.

The IAB donor DU transmits the data packet to an IAB donorcentralization unit (CU) according to the first information.

The IAB donor DU is the IAB node, or a DU node in an IAB donor, or a DUnode wiredly connected to a CU in the IAB donor.

The embodiment of the present disclosure further provides a method forperforming relay forwarding on integrated access and backhaul (IAB)links, including steps described below.

An IAB donor receives a data packet from a core network element or anapplication layer.

The IAB donor transmits the data packet to an IAB node to directly orindirectly transmit the data packet to a UE through the IAB node.

The embodiment of the present disclosure further provides a method forperforming relay forwarding on integrated access and backhaul (IAB)links, including steps described below.

An IAB node receives a data packet from an IAB donor.

The IAB node transmits the data packet to a user equipment (UE).

The embodiment of the present disclosure further provides an informationacquisition method, including steps described below.

An integrated access and backhaul (IAB) links node acquires firstmapping related information; where the first mapping related informationincludes at least one of:

a mapping relationship between QoS class identifier (QCI) anddifferentiated services code point (DSCP); a mapping relationshipbetween a 5th-generation QoS identifier (5QI) and type of service (TOS);a mapping relationship between the QCI and the TOS; a mappingrelationship between the 5QI and the QCI; a mapping relationship betweenthe QCI and the QCI; a mapping relationship between the 5QI and the 5QI;a mapping relationship between a quality of service flow identifier(QFI) and the QFI; a mapping relationship between a bearer identifierand the QFI; or a mapping relationship between the bearer identifier andthe bearer identifier.

The embodiment of the present disclosure further provides an informationacquisition method, including steps described below.

An integrated access and backhaul (IAB) links donor distribution unit(DU) acquires mapping related information; where the mapping relatedinformation includes at least one of:

a mapping relationship between user equipment (UE) bearer informationand general packet radio service tunneling protocol (GTP) tunnelinformation of an F1 interface; a mapping relationship between the GTPtunnel information of the F1 interface, a target node identifier and UEbearer information; a mapping relationship between the GTP tunnelinformation of the F1 interface and the target node identifier; or amapping relationship between the GTP tunnel information of the F1interface.

The UE bearer information includes at least one of: a UE identifier or abearer identifier;

The GTP tunnel information of the F1 interface includes at least one of:an address or tunnel endpoint identifier (TEID) information;

The IAB donor DU is one of: the IAB node, a DU node in an IAB donor, anda DU node wiredly connected to a CU in the IAB donor.

The embodiment of the present disclosure further provides an integratedaccess and backhaul (IAB) links node in an IAB donor, including amemory, a processor, and a computer program stored in the memory andexecutable on the processor, where when executing the computer program,the processor implements the method applied to the IAB node in anyembodiment described above.

The embodiment of the present disclosure further provides an integratedaccess and backhaul (IAB) links donor node in IAB, including a memory, aprocessor, and a computer program stored in the memory and executable onthe processor, where when executing the computer program, the processorimplements the method applied to the IAB donor node in any embodimentdescribed above.

The embodiment of the present disclosure further provides acomputer-readable storage medium configured to store computer-executableinstructions for executing the method in any embodiment when executed bya processor.

Solutions of the above embodiment may perform relay forwarding in theIAB architecture so as to correctly transmit and receive the UE's data.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1A is a schematic diagram of an IAB deployment scenario where acentralization unit (CU) is not separated from a distribution unit (DU).

FIG. 1B is a schematic diagram of an IAB deployment scenario where thecentralization unit (CU) is separated from the distribution unit (DU).

FIG. 2 is a schematic diagram of a protocol stack between a userequipment (UE) and a user plane function (UPF) according to embodimentone of the present disclosure, the CU is not configured with an adaptorlayer.

FIG. 3 is a schematic diagram of another protocol stack between the UEand the UPF according to embodiment one of the present disclosure, andthe CU is configured with the adaptor layer.

FIG. 4A is a schematic diagram of a protocol stack between the UE andthe UPF according to embodiment two of the present disclosure, a GTPuser plane (GTP-U) protocol layer exists above the adaptor layer, andthe CU is not configured with the adaptor layer.

FIG. 4B is a schematic diagram of another protocol stack between the UEand the UPF according to embodiment two of the present disclosure.

FIG. 5 is a schematic diagram of another protocol stack between the UEand the UPF according to embodiment two of the present disclosure, theGTP-U protocol layer exists above the adaptor layer, and the CU isconfigured with the adaptor layer.

FIG. 6 is a schematic diagram of a protocol stack between the UE and theUPF according to embodiment three of the present disclosure.

DETAILED DESCRIPTION

Objects, technical solutions and advantages of the present disclosurewill be clearer from a detailed description of embodiments of thepresent disclosure in conjunction with the drawings. It is to be notedthat if not in collision, the embodiments and features therein in thepresent application may be combined with each other.

Data of a user equipment (UE) may need to be transmitted throughmulti-hop relay backhaul links between an access node and a corenetwork, as shown in FIG. 1A. An uplink data packet of the UE may besent to an IAB donor through two IAB nodes, and then sent to a NextGeneration Core (NGC). In this case, an IAB node 1 to which the UE isdirectly connected is called a serving IAB node, and an IAB node 2 maybe called an intermediate IAB node. In FIG. 1A, the data of the UE needsto be transmitted to the core network through the IAB node 1, the IABnode 2 and the IAB donor sequentially.

In addition, it is an important technical feature in the New Radio (NR)to support a centralized unit (CU)/distributed unit (DU) separateddeployment. When the CU/DU is separated, an IAB architecture is as shownin FIG. 1B, the IAB node 1 and the IAB node 2 each have a distributionunit (DU) and a mobile terminal (MT) (which may also be called as UE)functions, and the IAB donor has a DU and a CU function.

The following are the embodiments of the present disclosure. It shouldbe noted that the following multiple embodiment methods are applicableto scenarios where the CU/DU is deployed separately or not. The UE maybe a NR UE or an LTE UE. The UE may be accessed in a standalone (SA)mode or a non-standalone (NSA) mode. The UE may be accessed in a dualconnection mode or a single connection mode. The IAB node may access toa network in the standalone (SA) mode or the non-standalone (NSA) mode.The IAB node may access to the network in the dual connection mode orthe single connection mode. An adaptor layer may be located above aradio link control (RLC) layer, or between the RLC layer and the mediaaccess control (MAC) layer, or an adaptor layer function is located inthe RLC or MAC layer.

In an embodiment, a method for performing relay forwarding on integratedaccess and backhaul (IAB) links is provided, the method is applied in anuplink direction and on an IAB node side. The method includes stepsdescribed below.

In step one, a first IAB node receives a data packet.

In step two, the first IAB node transmits the data packet to an IABdonor.

Optionally, the step in which the first IAB node transmits the datapacket to the IAB donor includes a step described below. The first IABnode obtains routing related information, and transmits the data packetto the IAB donor according to the routing related information.

Optionally, the step in which the first IAB node receives the datapacket includes steps described below.

the first IAB node receives the data packet from a user equipment (UE);or

The first IAB node receives the data packet from an application layer ofthe first IAB node itself.

The first IAB node receives the data packet from another IAB node,

where the data packet is user-plane data or control-plane signaling.

Optionally, the step in which the first IAB node transmits the datapacket to the IAB donor includes steps described below.

The first IAB node transmits the data packet to the IAB donor directly;or, the first IAB node forwards the data packet to another IAB node, andtransmits the data packet to the IAB donor through the another IAB nodedirectly or indirectly.

Optionally, the routing related information includes at least one of: asource node identifier;

a source node address; a target node identifier; a target node address;routing path information;

a bearer type; a bearer identifier; a master base station or a masternode identifier; a master base station or a master node address; asecondary base station or a secondary node identifier; a secondary basestation or a secondary node identifier; routing path information aboutrouting to a master node or to the master base station; routing pathinformation about routing to a secondary node or to the secondary basestation; a next-hop node ID; a next-hop address; or general packet radioservice tunneling protocol (GTP) tunnel information.

The UE identifier is one of: a 5G base station centralized unit userequipment F1 interface access point identifier (gNB-CU UE F1AP ID), agNB-DU UE F1AP ID, a cell radio network temporary identifier (C-RNTI),an S1 interface access point identifier (S1 AP ID), an X2 AP ID, an NGAP ID and an Xn AP ID.

The bearer identifier is one of: a data radio bearer identifier (DRBID), a signaling radio bearer identifier (SRB ID), a logical channelidentifier (LCID), a quality of service flow identifier (QFI), and aflow identifier.

The target node identifier is one of: a DU identifier, a CU identifier,a base station identifier, a user plane function (UPF) identifier, anaccess and mobility management function (AMF) identifier, a cellidentifier and a target index number.

Optionally, the step in which the first IAB node obtains routing relatedinformation includes one or more manners described below.

The first IAB node obtains the routing related information from anaccess side network element through radio resource control (RRC)signaling, F1 signaling, X2 signaling, Xn signaling or other interfaceinformation.

The first IAB node obtains the routing related information from a corenetwork element through S1 signaling, NG signaling, or other interfaceinformation.

The first IAB node obtains the routing related information from anapplication server.

The first IAB node obtains the routing related information from anadaptor layer header of the received data packet.

The first IAB node obtains the routing related information from anInternet protocol (IP) layer header of the received data packet.

Optionally, the routing related information obtained by the first IABnode is configured at a granularity of a UE; or the routing relatedinformation is configured at a granularity of a UE's bearer, where thefirst IAB node obtains a bearer identifier and routing relatedinformation corresponding to the bearer identifier; or the routingrelated information is configured at a granularity of a UE's bearertype, where the first IAB node obtains a bearer type and routing relatedinformation corresponding to the bearer type.

Optionally, the step in which the first IAB node transmits the datapacket to the IAB donor includes a step described below.

The IAB donor adds an adaptor layer header to the data packet, where theadaptor layer header includes at least one of: a source node identifier,a target node identifier, a UE identifier to which the data packetbelongs, and a bearer identifier to which the data packet belongs, achannel identifier to which the data packet belongs, routing pathinformation, Quality of Service (QoS) related information, generalpacket radio service tunneling protocol (GTP) tunnel information,control plane indication information, user plane indication informationor protocol type indication information.

The protocol type indication information may include one of: an F1, anF1 control plane, an F1 user plane, an IP, a non-IP, a stream controltransmission protocol (SCTP), an NG, an S1, an Xn and an X2.

Optionally, the adding an adaptor layer header is performed by anadaptor layer located above a radio link control (RLC) layer; or anadaptor layer located between the RLC layer and a media access control(MAC) layer; or an adaptor layer functional entity located at the RLClayer; or an adaptor layer functional entity located at the MAC layer.

Optionally, the step in which the first IAB node transmits the datapacket to the IAB donor includes: transmitting the data packet to anext-hop node in modes described below.

The first IAB node maps, according to a mapping rule and at least one ofa bearer to which the data packet belongs or Quality of Service (QoS)related information of a QoS flow, the data packet to a correspondingradio bearer to transmit to the next-hop node, where the mapping ruleincludes at least one of: a packet mapping rule, a QoS rule, a mappingrule between the QoS related information and differentiated servicescode point (DSCP), and a mapping rule between the QoS relatedinformation and type of service (TOS).

The first IAB node maps, according to the corresponding mapping rule andbased on one of a logical channel or radio bearer of a UE to which thedata packet belongs, or a logical channel or radio bearer of aprevious-hop IAB node related to the data packet, the data packet to aradio bearer or logical channel of the first IAB node to transmit to thenext-hop node.

Optionally, the step in which the first IAB node transmits the datapacket to the IAB donor includes steps described below.

The first IAB node maps, according to a radio bearer to which the datapacket belongs and a mapping relationship between the radio bearer and ageneral packet radio service tunneling protocol (GTP) tunnel of an F1interface, the data packet to the GTP tunnel of the F1 interfacecorresponding to the radio bearer to which the data packet belongs.

The first IAB node adds an adaptor layer header to the data packet,where the adaptor layer header includes at least one of: a source nodeidentifier, a target node identifier, a user equipment (UE) identifierto which the data packet belongs, routing path information, Quality ofService (QoS) related information, GTP tunnel information, control planeindication information, user plane indication information, or protocoltype indication information.

Optionally, after the first IAB node maps the data packet to thecorresponding GTP tunnel of the F1 interface, the method furtherincludes steps described below.

The first IAB node maps the data packet added with the adaptor layerheader to the logical channel or radio bearer, and transmits the datapacket to a next-hop node; or, the first IAB node takes the data packetencapsulated by an F1 user plane interface (F1-U) as a data packet ofthe first IAB node itself that serves as a UE, maps an F1-U GTP bearerof the UE to which the encapsulated data packet belongs to the logicalchannel, radio bearer or QoS flow of the first IAB node, and transmitsthe encapsulated data packet through a protocol data unit (PDU) sessionof the first IAB node itself.

Optionally, after the first IAB node obtains the routing relatedinformation, the method further includes steps described below.

The first IAB node determines a target node and the next-hop node of thedata packet or a routing path according to the routing relatedinformation.

The target node is the IAB donor, or the gNB-CU in the IAB donor, or thegNB-DU in the IAB donor, or the gNB-DU connected to the gNB-CU in theIAB donor, or the UPF, or the AMF, or the base station, or the IAB node.

The next-hop node is the IAB donor or the IAB node.

Optionally, the step in which the first IAB node obtains the routingrelation information includes a step described below.

The first IAB node obtains the routing related information from anadaptor layer header of the received data packet.

After the first IAB node obtains the routing related information, themethod further includes at least one of steps described below. The firstIAB node searches, according to the routing related information, arouting table to determine the next-hop node, where the next-hop node isthe IAB donor or the IAB node; or adds an adaptor layer header.

The target node is the IAB donor, or the gNB-CU in the IAB donor, or thegNB-DU in the IAB donor, or the gNB-DU connected to the gNB-CU in theIAB donor, or the UPF, or the AMF, or the base station, or the IAB node.

The next-hop node is the IAB donor or the IAB node.

The embodiment of the present disclosure further provides a method forperforming relay forwarding on integrated access and backhaul (IAB)links, the method is applied in an uplink direction and on an IAB donorside. The method includes steps described below.

In step A, an IAB donor distribution unit (DU) receives a data packettransmitted by an IAB node.

In step B, the IAB donor DU obtains first information, where the firstinformation includes at least one of: a source node identifier, a targetnode identifier, a UE identifier to which the data packet belongs, and abearer identifier to which the data packet belongs, a channel identifierto which the data packet belongs, routing path information, Quality ofService (QoS) related information, general packet radio servicetunneling protocol (GTP) tunnel information, control plane indicationinformation, user plane indication information or protocol typeindication information.

In step C, the IAB donor DU transmits the data packet to an IAB donorcentralization unit (CU) according to the first information.

The IAB donor DU is the IAB node, a DU node in an IAB donor, or a DUnode wiredly connected to a CU in the IAB donor.

Optionally, the step in which the IAB donor DU obtains the firstinformation includes a step described below.

The IAB donor DU obtains at least part of the first information from anadaptor layer header of the data packet.

Optionally, the step in which the IAB donor DU transmits the data packetto the IAB donor centralization unit (CU) according to the firstinformation includes steps described below.

The IAB donor DU maps the data packet to a corresponding GTP tunnel ofan F1 interface according to the first information, and transmits thedata packet to the IAB donor CU.

After adding an adaptor layer header to the data packet, the IAB donorDU transmits the data packet to the IAB donor CU through the GTP tunnelof the F1 interface.

The adaptor layer header includes at least one of: the source nodeidentifier, the target node identifier, the UE identifier to which thedata packet belongs, and the bearer identifier to which the data packetbelongs, the channel identifier to which the data packet belongs, therouting path information, the QoS related information, the GTP tunnelinformation, the control plane indication information, the user planeindication information or the protocol type indication information.

Optionally, the adding an adaptor layer header is performed by anadaptor layer located above a radio link control (RLC) layer; or anadaptor layer located between the RLC layer and a media access control(MAC) layer; or an adaptor layer functional entity located at the RLClayer; or an adaptor layer functional entity located at the MAC layer.

Optionally, the step in which the IAB donor DU maps the data packet tothe corresponding GTP tunnel of the F1 interface and transmits the datapacket to the IAB donor centralization unit (CU) according to the firstinformation includes steps described below.

The IAB donor DU determines the GTP tunnel of the F1 interfacecorresponding to a UE and a bearer to which the data packet belongs,maps the data packet to the GTP tunnel of the F1 interface and transmitsthe data packet to the IAB donor CU according to a corresponding mappingrule, so that the IAB donor CU identifies the UE and the bearer to whichthe data packet belongs according to tunnel information in a GTP-Upacket header.

In response to acquiring the GTP tunnel information from the data packetand performing processing and encapsulation in a GTP-U protocol layer,the IAB donor DU transmits the GTP tunnel information included in theGTP-U packet header to the IAB donor CU, so that the IAB donor CUidentifies the UE and the bearer to which the data packet belongsaccording to the GTP tunnel information in the GTP-U packet header; or,in response to acquiring the GTP tunnel information from the data packetand performing processing and encapsulation in the GTP-U protocol layer,the IAB donor DU transmits GTP tunnel information which is between theIAB donor CU and the IAB donor DU corresponding to the GTP tunnelinformation and included in the GTP-U packet header to the IAB donor CU,so that the IAB donor CU identifies the UE and the bearer to which thedata packet belongs according to the GTP tunnel information in the GTP-Upacket header.

Optionally, in response to the adaptor layer header added by the IABdonor DU to the data packet does not include the UE identifier to whichthe data packet belongs and the bearer identifier to which the datapacket belongs, the method further includes steps described below.

The IAB host DU determines, based on a correspondence relationship amongthe bearer, the UE and a GTP-U tunnel established by a GTP-U above theadaptor layer, the UE and the bearer to which the data packet belongsaccording to the GTP-U tunnel to which the data packet belongs.

The embodiment of the present disclosure further provides a method forperforming relay forwarding on integrated access and backhaul (IAB)links, the method is applied in a downlink direction and on an IAB donorside. The method includes steps described below.

In step a, an IAB donor receives a data packet from a core networkelement or an adaptor layer.

In step b, the IAB donor sends the data packet to the IAB node todirectly or indirectly transmit the data packet to the UE through theIAB node.

Optionally, the step in which the IAB donor transmits the data packet toa second IAB node includes a step described below.

The IAB donor adds an adaptor layer header to the data packet after theIAB donor parses the data packet in a corresponding protocol layer,where the adaptor layer header carries at least one of: a source nodeidentifier, a target node identifier, a UE identifier to which the datapacket belongs, and a bearer identifier to which the data packetbelongs, a channel identifier to which the data packet belongs, routingpath information, Quality of Service (QoS) related information, generalpacket radio service tunneling protocol (GTP) tunnel information,control plane indication information, user plane indication informationor protocol type indication information.

Optionally, the step in which the adaptor layer header is added isperformed by an adaptor layer located above a radio link control (RLC)layer; or an adaptor layer located between the RLC layer and a mediaaccess control (MAC) layer; or an adaptor layer functional entitylocated at the RLC layer; or an adaptor layer functional entity locatedat the MAC layer.

Optionally, the IAB donor includes an IAB donor centralization unit CUand/or an IAB donor distribution unit (DU).

The step in which the IAB donor transmits the data packet to the secondIAB node includes steps described below.

the IAB donor CU maps the data packet to a GTP tunnel corresponding to aUE and a bearer to which the data packet belongs, transmits the mappeddata packet to the IAB donor DU, the IAB donor DU transmits the datapacket to a next-hop node after encapsulating an identifier of the UEand a bearer identifier in an adaptor layer header; or, the IAB donor CUcarries GTP tunnel information allocated by a serving IAB node in a GTPuser plane (GTP-U) header of the data packet to be transmitted to theIAB donor DU, and the IAB donor DU transmits the data packet to thenext-hop node after obtaining the GTP tunnel information andencapsulating the GTP tunnel information in the adaptor layer header;or, the IAB donor CU carries first GTP tunnel information between theIAB donor CU and the IAB donor DU in the GTP-U header of the data packettransmitted to the IAB donor DU, the IAB donor DU determines second GTPtunnel information allocated by the serving IAB node corresponding tothe first GTP tunnel information, and after encapsulating the second GTPtunnel information in the adaptor layer header, transmits the datapacket to the next-hop node; or, the IAB donor CU transmits the datapacket to the DU after adding the adaptor layer header to the datapacket, where the adaptor layer header carries at least one of: a sourcenode identifier, a target node identifier, a UE identifier to which thedata packet belongs, and a bearer identifier to which the data packetbelongs, a channel identifier to which the data packet belongs, routingpath information, Quality of Service (QoS) related information, generalpacket radio service tunneling protocol (GTP) tunnel information,control plane indication information, user plane indication informationor protocol type indication information; The IAB donor CU maps the datapacket to the corresponding GTP tunnel, and after performing GTP-Uprocessing and encapsulation, adds the adaptor layer header to the datapacket, transmits the data packet to the IAB donor DU, where the adaptorlayer header carries at least one of: the source node identifier, thetarget node identifier, the channel identifier to which the data packetbelongs, the routing path information, the QoS related information, theGTP tunnel information, the control plane indication information, theuser plane indication information or the protocol type indicationinformation.

Optionally, the step in which the IAB donor transmits the data packet toa second IAB node further includes steps described below.

The DU receives the data packet transmitted by the IAB donor CU, andtransmits the data packet to the next-hop node after adding the adaptorlayer header to the data packet, where the adaptor layer header carriesat least one of: the source node identifier, the target node identifier,the UE identifier to which the data packet belongs, and the beareridentifier to which the data packet belongs, the channel identifier towhich the data packet belongs, the routing path information, the QoSrelated information, the GTP tunnel information, the control planeindication information, the user plane indication information or theprotocol type indication information; or, the DU receives the datapacket transmitted by the IAB donor CU, and transmits the data packet tothe next-hop node after adding the adaptor layer header to the datapacket, where the adaptor layer header carries at least one of: thesource node identifier, the target node identifier, the channelidentifier to which the data packet belongs, the routing pathinformation, the QoS related information, the GTP tunnel information,the control plane indication information, the user plane indicationinformation or the protocol type indication information; or, afterreceiving the data packet transmitted by the IAB donor CU, the DU mapsthe GTP tunnel between the IAB donor CU and the IAB donor DU to whichthe data packet belongs to the GTP tunnel between the IAB donor CU andthe serving IAB node corresponding to the data packet, and transmits thedata packet to the next-hop node after GTP-U encapsulation is performedand the adaptor layer header is added, where the adaptor layer headercarries at least one of: the source node identifier, the target nodeidentifier, the channel identifier to which the data packet belongs, therouting path information, the QoS related information, the GTP tunnelinformation, the control plane indication information, the user planeindication information or the protocol type indication information.

The embodiment of the present disclosure further provides a method forperforming relay forwarding on integrated access and backhaul links(IAB), the method is applied in a downlink direction and on an IAB nodeside. The method includes steps described below.

In step I, an IAB node receives a data packet from an IAB donor.

In step II, the IAB node transmits the data packet to a user equipment(UE).

Optionally, the step in which the IAB node transmits the data packet tothe user equipment (UE) includes a step described below.

The IAB node acquires second information from an adaptor layer header,determines a next-hop node according to the second information, andtransmits the data packet to the next-hop node, where the secondinformation includes at least one of: a source node identifier, a targetnode identifier, a UE identifier to which the data packet belongs, and abearer identifier to which the data packet belongs, a channel identifierto which the data packet belongs, routing path information, Quality ofService (QoS) related information, general packet radio servicetunneling protocol (GTP) tunnel information, control plane indicationinformation, user plane indication information or protocol typeindication information.

Optionally, the step in which the IAB node transmits the data packet tothe user equipment (UE) includes a step described below.

After adding an adaptor layer header to the data packet, the IAB nodetransmits the data packet to the next-hop node, where the secondinformation in the adaptor layer header includes at least one of: asource node identifier, a target node identifier, a UE identifier towhich the data packet belongs, and a bearer identifier to which the datapacket belongs, a channel identifier to which the data packet belongs,routing path information, Quality of Service (QoS) related information,general packet radio service tunneling protocol (GTP) tunnelinformation, control plane indication information, user plane indicationinformation or protocol type indication information.

Optionally, the step in which the IAB node transmits the data packet tothe user equipment (UE) includes a step described below.

The IAB node determines corresponding QoS related information accordingto a QoS flow or a bearer to which the data packet belongs or determinesthe QoS related information according to the second information, andmaps the data packet to a radio bearer, a logical channel or the QoSflow corresponding to the QoS related information and transmits the datapacket to the next-hop node; or, the IAB node determines the bearer andthe UE to which the data packet belongs according to the UE identifierand the bearer identifier in the second information or according to GTPtunnel information in the second information, and then transmits thedata packet to the UE through the radio bearer, the logical channel orthe QoS flow corresponding to the bearer and the UE; or, the IAB nodeobtains the GTP tunnel information by parsing a GTP user plane (GTP-U)protocol layer, determines the bearer and the UE to which the datapacket belongs according to the GTP tunnel information, and thentransmits the data packet to the UE through the radio bearer, thelogical channel or the QoS flow corresponding to the bearer and the UE.

The embodiment of the present disclosure further provides an informationacquisition method, including a step described below.

An integrated access and backhaul (IAB) links node acquires firstmapping related information; where the first mapping related informationincludes at least one of: mapping relationship between a QCI and a DSCP;a mapping relationship between a 5QI and a TOS; a mapping relationshipbetween the QCI and the TOS; a mapping relationship between the 5QI andthe QCI; a mapping relationship between the QCI and the QCI; a mappingrelationship between the 5QI and the 5QI; a mapping relationship betweena quality of service flow identifier (QFI) and the QFI; a mappingrelationship between a bearer identifier and the QFI; or a mappingrelationship between the bearer identifier and the bearer identifier.

In an embodiment, a manner for an integrated access and backhaul (IAB)links node acquiring first mapping related information includes at leastone of steps described below.

The IAB node obtains the first mapping related information from anaccess side network element through radio resource control (RRC)signaling, F1 signaling, X2 signaling, Xn signaling or other interfaceinformation; the IAB node obtains the first mapping related informationfrom a core network element through S1 signaling, NG signaling, or otherinterface information; or a first IAB node obtains the first mappingrelated information from an application server.

The embodiment of the present disclosure further provides an informationacquisition method, including a step described below.

An integrated access and backhaul (IAB) links donor distribution unit(DU) acquires mapping related information; where the mapping relatedinformation includes at least one of: a mapping relationship betweenuser equipment (UE) bearer information and general packet radio servicetunneling protocol (GTP) tunnel information of an F1 interface; amapping relationship between the GTP tunnel information of the F1interface, a target node identifier and UE bearer information; a mappingrelationship between the GTP tunnel information of the F1 interface andthe target node identifier; or a mapping relationship between the GTPtunnel information of the F1 interface.

The UE bearer information includes at least one of: a UE identifier or abearer identifier.

The GTP tunnel information of the F1 interface includes: an addressand/or tunnel endpoint identifier (TEID) information.

The IAB donor DU is the IAB node, or a DU node in an IAB donor, or a DUnode wiredly connected to a CU in the IAB donor.

The embodiment of the present disclosure further provides an integratedaccess and backhaul (IAB) links donor node in IAB, including a memory, aprocessor, and a computer program stored in the memory and executable onthe processor, where when executing the computer program, the processorimplements any method executed by the IAB node described above.

The embodiment of the present disclosure further provides an integratedaccess and backhaul (IAB) links donor node in IAB, including a memory, aprocessor, and a computer program stored in the memory and executable onthe processor, where when executing the computer program, the processorimplements any method executed by the IAB donor node described above.

An embodiment of the present disclosure further provides acomputer-readable storage medium configured to store a computer programfor executing any method described above when executed by a processor.

Embodiment One

This embodiment method is a method for routing according to adaptorlayer information. A protocol stack between a user equipment (UE) and auser plane function (UPF) is as shown in FIGS. 2 and 3. An adaptor layeris located above a radio link control (RLC) layer of an IAB node and anIAB donor. It should be noted that the adaptor layer may also be locatedbetween the RLC layer and a media access control (MAC) layer, or anadaptor layer function is located in the RLC layer or the MAC layer.

An uplink data forwarding process using this embodiment method is asfollows.

In step one, a data packet of the UE is transmitted to an IAB node 1through an air interface after being encapsulated and processed by acorresponding protocol layer (such as a service data adaptation protocol(SDAP) layer/packet data convergence protocol (PDCP) layer/RLC layer/MAClayer/physical layer (PHY)).

In step two, after receiving the data packet from the UE and performingthe corresponding parsing in the PHY/MAC/RLC layer, the IAB node 1determines a target node and a next-hop node of the data packetaccording to the obtained routing information, or determines a routingpath.

In this embodiment, the target node is the IAB donor, or a gNB-CU in theIAB donor, or a gNB-DU in the IAB donor, or the gNB-DU connected to thegNB-CU in the IAB donor, or a UPF, or an access and mobility managementfunction (AMF), or a base station, or the IAB node.

The routing related information includes at least one of:

1) a target node identifier;

2) a target node address, such as a transport network layer (TNL)address or an IP address;

3) routing path information, which may include one of: a routing pathidentifier, a routing path number, a routing path index number, such asa path identifier or a number or index information in a routing tableconfigured in the IAB node 1;

3) a bearer type, which includes at least one of: a master cell group(MCG) bearer, a secondary cell group (SCG) bearer, a split bearer, amaster node (MN) terminated SCG bearer and a secondary node (SN)terminated MCG bearer;

4) a master base station or a master node identifier, which may beidentification information of the base station or a centralized unit(CU) or a distributed unit (DU);

5) a master base station or a master node address, which may be addressinformation of the base station or the CU or the DU;

6) a secondary base station or a secondary node identifier, which may beidentification information of the base station or the CU or the DU;

7) a secondary base station or a secondary node address, which may beaddress information of the base station or the CU or the DU;

8) routing path information about routing to the master base station ora master node, including one of: a routing path identifier, a routingpath number, a routing path index number, such as the path identifier orthe number or the index information in the routing table configured inthe IAB node 1;

9) routing path information about routing to the secondary base stationor a secondary node, including one of: the routing path identifier, therouting path number, the routing path index number, such as the pathidentifier or the number or the index information in the routing tableconfigured in the IAB node 1;

10) a next-hop node ID, where the next-hop node may be the IAB donor, orthe gNB-CU in the IAB donor, or the gNB-DU in the IAB donor, or thegNB-DU connected to the gNB-CU in the IAB donor, or the UPF, or the AMF,or the base station, or the IAB node; or

11) a next-hop node address; a transport network layer (TNL) address orthe IP address of the next-hop node.

In this embodiment, the IAB node 1 may obtain the routing relatedinformation from an access side network element through RRC signaling,F1 signaling, X2 signaling, or Xn signaling; where the access sidenetwork element is one of: the gNB-CU, the IAB donor, a gNB, an eNB; orthe IAB node 1 may obtain the routing related information from a corenetwork element through S1 signaling or NG signaling; or the IAB node 1may obtain the routing related information from an application server;

12) general packet radio service tunneling protocol (GTP) tunnelinformation;

13) a source node identifier;

14) a source node address; or

15) a bearer identifier.

In this embodiment, the IAB node 1 may obtain the routing relatedinformation from an access side network element through the RRCsignaling, the F1 signaling, the X2 signaling, or the Xn signaling;where the access side network element is one of: the gNB-CU, the IABdonor, a gNB, an eNB; or the IAB node 1 may obtain the routing relatedinformation from a core network element through S1 signaling or NGsignaling; or the IAB node 1 may obtain the routing related informationfrom an application server.

In this embodiment, the routing related information may be configured atthe granularity of the UE; or the routing related information may beconfigured at the granularity of the UE's bearer, that is, thecorresponding routing related information is configured for each UE'sbearer; or the routing related information may also be configured at agranularity of a UE's bearer type, that is, the corresponding routinginformation is configured for each UE's bearer type. The IAB node1 maydetermine the target node and/or the next-hop node of the data packetaccording to an RLC channel or a bearer identifier or a bearer typeand/or corresponding routing related information to which the datapacket received from the UE belongs. Optionally, for the split bearer ofthe UE, the bearer's data may be forwarded to two or more differenttarget nodes.

In step three, the IAB node 1 adds an adaptor layer header to the parsedPDCP PDU, the adaptor layer header includes at least one of: the sourcenode identifier, the target node identifier, the UE identifier to whichthe data packet belongs, and the bearer identifier to which the datapacket belongs, the channel identifier to which the data packet belongs,the routing path information, the Quality of Service (QoS) relatedinformation, the general packet radio service tunneling protocol (GTP)tunnel information, the control plane indication information, the userplane indication information or the protocol type indicationinformation. The GTP tunnel information includes the TNL address and/orGTP TEID information, for example, GTP tunnel information correspondingto the UE bearer allocated by a donor CU. The protocol type indicationinformation includes one of: an F1, an F1 control plane, an F1 userplane, an IP, a non-IP, an SCTP, an NG, an S1, an Xn and an X2.

Optionally, the IAB node 1 may obtain UE bearer information andcorresponding GTP tunnel information from the CU, for example, it may beobtained through the RRC signaling or the F1 signaling.

In step four, the IAB node 1 determines that the next-hop node is an IABnode 2, and then the data packet encapsulated by the adaptor layer istransmitted to the IAB node 2 through the RLC channel or the radiobearer between the IAB node 1 and the IAB node 2.

The IAB node 1 needs to map the UE's data packet to the RLC channel orthe radio bearer of the IAB node 1, so as to transmit the data packet tothe IAB node 2. Specifically, the IAB node 1 may map the UE's datapacket to the RLC channel or the radio bearer of the IAB node 1 based onmethods one to three described below.

Method one: the IAB node1 maps the UE's data packet to the correspondingbearer according to specific mapping rules.

Specifically, the IAB node1 obtains the bear identifier or a QCI or 5QIor QFI value of the QoS flow or the bearer to which the received UE datapacket belongs, and then performs corresponding mappings according toconfigured bearer mapping relationship information. The bearer mappingrelationship information includes at least one of:

a mapping relationship between a QCI and a DSCP;

a mapping relationship between the 5QI and the TOS;

a mapping relationship between the QCI and the TOS;

a mapping relationship between the 5QI and the TOS;

a mapping relationship between the 5QI and the QCI;

a mapping relationship between the QCI and the QCI;

a mapping relationship between the 5QI and the 5QI;

a mapping relationship between a quality of service flow identifier(QFI) and the QFI;

a mapping relationship between a bearer identifier and the QFI; or

In a case where the IAB node1 obtains a corresponding DSCP or TOS valueaccording to the QCI or 5QI or QFI value of the QoS flow or the bearerto which the UE data packet belongs and the bearer mapping relationshipinformation, the IAB node 1 maps the UE data packet to the correspondingradio bearer or the RLC channel or the QoS flow of the corresponding IABnode1 according to the DSCP or TOS value and the configured packetmapping rules (such as a packet filter set or a traffic flow template(TFT)). Optionally, if the IAB node1 maps the UE data packet to thecorresponding QoS flow according to the DSCP or TOS value and theconfigured packet mapping rules, then the IAB node1 maps the QoS flow tothe radio bearer, and transmits the UE data packet to the IAB node2through the corresponding radio bearer.

Method two: the IAB node1 obtains the QFI or 5QI or QCI value of the QoSflow or the bearer to which the received UE data packet belongs from thereceived UE data packet, and then maps the data packet to the RLCchannel or the bearer or the QoS flow corresponding to the QCI or 5QI orQFI value in the configured QoS rules or the TFT. If the UE data packetis mapped to the corresponding QoS flow, the IAB node1 then maps the QoSflow to the radio bearer, and transmits the UE data packet to the IABnode2 through the corresponding radio bearer.

Method three: the IAB node 1 performs the corresponding mappingaccording to a mapping relationship between a logic channel of the IABnode 1 and a logical channel of the configured UE (such as a mappingrelationship between logical channel IDs (LCIDs)) or a mappingrelationship between a radio bearer of the IAB node 1 and a radio bearerof the UE (such as a mapping relationship between radio bearer IDs(RBIDs)). The mapping relationship may be a predefined or one-to-onecorrespondence relationship, or the mapping relationship may beconfigured in one of the following manners: the F1 signaling, the RRCsignaling, the X2 signaling, the Xn signaling, the S1 signaling and theNG signaling.

In step five, the IAB node 2 parses the data packet in a correspondingprotocol layer (such as the PHY/MAC/RLC/adaptor layer) after receivingthe data packet, and obtains information in the adaptor layer headersuch as the source node identifier, the target node identifier, the UEidentifier to which the data packet belongs, and the bearer identifierto which the data packet belongs, the channel identifier to which thedata packet belongs, the routing path information, the Quality ofService (QoS) related information, the general packet radio servicetunneling protocol (GTP) tunnel information, the control planeindication information, the user plane indication information or theprotocol type indication information. Alternatively, the IAB node 2 onlyreads the information in the adaptor layer header, but does not removethe adaptor layer header. In this case, the IAB node 2 does notencapsulate the adaptor layer header. The IAB node 2 determines thetarget node according to the information in the adaptor layer header,and determines the next-hop node as the target node (donor DU) bychecking the routing table.

Optionally, the IAB node 2 adds the adaptor layer header to the datapacket, where the adaptor layer header includes at least one of: thesource node identifier, the target node identifier, the UE identifier towhich the data packet belongs, the bearer identifier to which the datapacket belongs, the channel identifier to which the data packet belongs,the routing path information, the Quality of Service (QoS) relatedinformation, the general packet radio service tunneling protocol (GTP)tunnel information, the control plane indication information, the userplane indication information, or the protocol type indicationinformation.

The IAB node 2 transmits the encapsulated data packet to the IAB donorthrough the RLC channel or the radio bearer between the IAB node 2 andthe IAB donor. The mapping between the RLC channel/radio bearer of theIAB node 1 and the RLC channel/radio bearer of the IAB node 2 may referto the method in the step four. The IAB node 2 performs thecorresponding RLC/MAC/PHY processing on the data packet and transmitsthe data packet to the IAB donor DU (the DU in the IAB donor or the DUconnected to the CU in the IAB donor).

In step six, the IAB donor DU parses the data packet in thePHY/MAC/RLC/adaptor layer and obtains at least one piece of thefollowing information: the source node identifier, the target nodeidentifier, the UE identifier to which the data packet belongs, and thebearer identifier to which the data packet belongs, the channelidentifier to which the data packet belongs, the routing pathinformation, the Quality of Service (QoS) related information, thegeneral packet radio service tunneling protocol (GTP) tunnelinformation, the control plane indication information, the user planeindication information or the protocol type indication information. TheIAB donor DU transmits the data packet to the IAB donor CU through anF1-U GTP tunnel between the IAB donor DU and the CU. The IAB donor DUneeds to acquire mapping related information (such as acquiring from theIAB donor CU), and the mapping related information includes at least oneof: a mapping relationship between user equipment (UE) bearerinformation and general packet radio service tunneling protocol (GTP)tunnel information of an F1 interface; a mapping relationship betweenthe GTP tunnel information of the F1 interface, a target node identifierand UE bearer information; a mapping relationship between the GTP tunnelinformation of the F1 interface and the target node identifier; or amapping relationship between the GTP tunnel information of the F1interface.

The UE bearer information includes at least one of: a UE identifier or abearer identifier.

The GTP tunnel information of the F1 interface includes: an address ortunnel endpoint identifier (TEID) information.

The IAB donor DU is the IAB node, a DU node in an IAB donor, and a DUnode wiredly connected to a CU in the IAB donor.

In FIG. 2, L1 represents the physical layer in a protocol stack model,and L2 represents a link layer in the protocol stack model.

In an architecture of FIG. 2, there is no adaptor layer on the CU. TheIAB donor DU maps each radio bearer of each UE to the F1-U GTP tunnel.The CU may be enabled to identify the UE and the bearer to which thedata packet belongs in three methods described below.

Method one, the donor DU obtains a signaling radio bearer (SRB) ID or adata radio bearer (DRB) ID of the UE and F1 GTP tunnel informationcorresponding to the donor DU from the donor CU. After receiving thedata packet, the IAB donor DU acquires the UE and the bearer identifiercarried in the adaptor layer header. The IAB donor DU may map the datapacket to the corresponding F1 GTP tunnel and transmit the data packetto the donor CU according to the acquired mapping relationship betweenthe SRB/DRB and the F1GTP tunnel, so that the CU may identify the UE andthe bearer to which the data packet belongs according to tunnelinformation in a GTP-U (also referred to as tunnel information in aGTP-U packet header), and deliver the data packet to a PDCP entity forthe corresponding bearer of the corresponding UE.

Method two, after receiving the data packet, the donor DU acquires theGTP tunnel information (the TNL address and/or the GTP TEID) carried inthe adaptor layer header, then when the donor DU performs processing andencapsulation in the GTP-U protocol layer, the donor DU transmits theGTP tunnel information which is in the adaptor layer header and includedin the GTP-U packet header to the donor CU, so that the CU may identifythe UE and the bearer to which the data packet belongs according to theGTP-U header information and delivers the data packet to the PDCP entityfor the corresponding bearer of the corresponding UE.

Method three, after receiving the data packet, the donor DU acquires theGTP tunnel information (the TNL address and/or the GTP TEID) carried inthe adaptor layer header. Then when performing the processing andencapsulation in the GTP-U protocol layer, according to the GTP tunnelmapping information configured for the donor DU by the CU, the donor DUtransmits the data packet included in the GTP-U packet header throughthe GTP tunnel information between the donor DU and the donor CUcorresponding to the GTP tunnel information in the adaptor layer headerto the donor CU, so that the CU may identify the UE and bearer to whichthe data packet belongs according to the GTP tunnel information, anddeliver the data packet to the PDCP entity for the corresponding bearerof the corresponding UE.

In an architecture of FIG. 3, optionally, the IAB donor DU encapsulatesthe adaptor layer header for the data packet. The adaptor layer headerincludes at least one of: the target node identifier, the UE identifierto which the data packet belongs, the bearer identifier to which thedata packet belongs, the channel identifier to which the data packetbelongs, the routing path information or the GTP tunnel information.Alternatively, the IAB donor DU only reads the information in theadaptor layer header, but does not remove the adaptor layer header. Inthis case, the IAB donor DU does not encapsulate the adaptor layerheader. The IAB donor DU transmits the data to the IAB donor CU throughthe F1-U GTP tunnel.

In step seven, in the architecture of FIG. 2, the donor CU identifiesthe UE and the bearer to which the data packet belongs according to theGTP-U tunnel information, and delivers the UE data packet to the PDCPentity for the corresponding bearer of the corresponding UE to performsubsequent parsing.

In the architecture of FIG. 3, the donor CU parses the adaptor layerheader and obtains at least one of: the source node identifier, thetarget node identifier, the UE identifier to which the data packetbelongs, the bearer identifier to which the data packet belongs, thechannel identifier to which the data packet belongs, the routing pathinformation, the QoS related information, the GTP tunnel information,the control plane indication information, the user plane indicationinformation or the protocol type indication information. Afteridentifying the UE and the bearer to which the data packet belongs, thedonor CU delivers the UE data packet to the PDCP entity for thecorresponding bearer of the corresponding UE to perform the subsequentparsing.

Then the SDAP layer of the donor CU finds an NG GTP-U tunnelcorresponding to a PDU session according to a RB ID to which the datapacket belongs and a flow ID of the UE in the SDAP packet header, andtransmits the UE data to the UPF through the NG GTP tunnel.

A downlink data forwarding process using this embodiment method is asfollows. It should be noted that steps described below may be used inany combination.

In step one, after receiving the UE data from the UPF, the IAB donor CUdetermines the QoS flow of the PDU session corresponding to the UE datapacket according to the QFI in the data packet header, and then maps theQoS flow to the corresponding radio bearer. The IAB donor needs todetermine the target node of the data packet. In this case, the targetnode of the data packet is the serving IAB node of the UE (i.e., the IABnode 1). For example, the IAB donor may determine the target node (theserving IAB node) of the data packet according to serving IAB nodeinformation in a UE context, or serving IAB node informationcorresponding to the radio bearer, or serving IAB node informationcorresponding to the bearer type. The IAB donor CU transmits the UE datapacket to the IAB donor DU (i.e., the DU in the IAB donor or the DUconnected to the CU in the IAB donor).

If the architecture shown in FIG. 2 is adopted, there is no adaptorlayer on the CU, and the donor CU transmits the UE data to the donor DUthrough an F1 GTP bearer.

In step two, the DU in the IAB donor or the DU connected to the CU inthe IAB donor receives the data packet. Optionally, the IAB donor DUacquires the mapping related information (such as acquiring from the IABdonor CU), and the mapping related information includes at least one of:a mapping relationship between user equipment (UE) bearer informationand general packet radio service tunneling protocol (GTP) tunnelinformation of an F1 interface; a mapping relationship between the GTPtunnel information of the F1 interface, a target node identifier and UEbearer information; a mapping relationship between the GTP tunnelinformation of the F1 interface and the target node identifier; or amapping relationship between the GTP tunnel information of the F1interface. The UE bearer information includes at least one of: a UEidentifier or a bearer identifier; the GTP tunnel information of the F1interface includes: an address and/or tunnel endpoint identifier (TEID)information.

The IAB donor DU is the IAB node, or a DU node in an IAB donor, or a DUnode wiredly connected to a CU in the IAB donor.

Optionally, the IAB node 1 identifies the UE and/or the bearer and/orthe target node to which the data packet belongs according to the abovemapping related information. The IAB node 1 may be encapsulated in theadaptor layer in one of methods described below.

Method one: the donor DU acquires the mapping relationship among the UE,the bearer and the GTP tunnel from the CU, and then determines the UEand the bearer to which the data packet belongs according to the GTPtunnel information. Then the donor DU encapsulates the UE identifier andthe bearer identifier in the adaptor layer header. Optionally, theadaptor layer header also includes the target node identifier and/orpath information, etc.

Method two: the GTP-U header of the data packet transmitted by the donorCU to the donor DU includes the GTP tunnel information (the TNL addressand/or the GTP TEID) allocated by the IAB node 1, and the donor DUobtains the GTP tunnel information after parsing and encapsulates theGTP tunnel information allocated by the IAB node 1 in the adaptor layerheader.

Method three: the donor DU acquires GTP tunnel information between thedonor DU and the donor CU and GTP tunnel information between thecorresponding IAB node 1 and the donor CU from the CU. After receivingthe UE data packet from the CU, the donor DU determines a GTP tunnelbetween the IAB node 1 and the donor CU corresponding to a GTP tunnelbetween the donor CU and the donor DU to which the data packet belongs,and encapsulates the tunnel information (the GTP tunnel between the IABnode 1 and the donor CU) in the adaptor layer header.

If the architecture of FIG. 3 is adopted, that is, the adaptor layer isprovided on the CU, and the CU in the IAB donor adds the adaptor layerheader for each PDCP PDU. The adaptor layer header includes at least oneof: the source node identifier, the target node identifier, the UEidentifier to which the data packet belongs, the bearer identifier towhich the data packet belongs, the channel identifier to which the datapacket belongs, the routing path information, the QoS relatedinformation, the GTP tunnel information, the control plane indicationinformation, the user plane indication information or the protocol typeindication information.

Alternatively, if the architecture shown in FIG. 3 is adopted, that is,the adaptor layer is provided on the CU, the CU in the IAB donor addsthe adaptor layer header to each PDCP PDU. The adaptor layer headerincludes at least one of: the target node identifier, the UE identifierto which the data packet belongs, the bearer identifier to which thedata packet belongs, the channel identifier to which the data packetbelongs, the routing path information and the QoS related information.The QoS related information is the QCI or 5QI value of the UE datapacket.

The IAB donor DU determines that the next-hop node is the IAB node 2.Optionally, the IAB donor DU maps the data packet to the QoS flow/bearerof the IAB node 2 with the corresponding QCI or 5QI value according tothe DSCP or TOS information and a mapping relationship between theconfigured DSCP/TOS and QCI/5QI in an IP header and transmits the datapacket to the IAB node 2.

In step three, after receiving the data packet, the IAB node 2 obtainsat least one of the following information by parsing the adaptor layer:the source node identifier, the target node identifier, the UEidentifier to which the data packet belongs, the bearer identifier towhich the data packet belongs, the channel identifier to which the datapacket belongs, the routing path information, the QoS relatedinformation, the GTP tunnel information, the control plane indicationinformation, the user plane indication information or the protocol typeindication information. The IAB node 2 determines a next-hop routingnode (the IAB node 1) according to the above information and the routingtable. Optionally, the IAB node 2 performs encapsulation in the adaptorlayer, where the adaptor layer header includes at least one of: thesource node identifier, the target node identifier, the UE identifier towhich the data packet belongs, the bearer identifier to which the datapacket belongs, the channel identifier to which the data packet belongs,the routing path information, the Quality of Service (QoS) relatedinformation, the general packet radio service tunneling protocol (GTP)tunnel information, the control plane indication information, the userplane indication information, or the protocol type indicationinformation. Optionally, the IAB node 2 determines QoS information (theQCI or 5QI or QFI value) according to the bearer or QoS flow to whichthe received data packet belongs, or determines the QoS informationaccording to adaptor layer header information of the received datapacket, and then maps the data packet on the QoS flow/bearer of the IABnode 1 with the corresponding QCI or 5QI or QF value and transmits thedata packet to the IAB node 1.

In step four, after receiving the data packet, the IAB node 1 obtains atleast one of the following information by parsing the adaptor layer: thesource node identifier, the target node identifier, the UE identifier towhich the data packet belongs, the bearer identifier to which the datapacket belongs, the channel identifier to which the data packet belongs,the routing path information, the QoS related information, the GTPtunnel information, the control plane indication information, the userplane indication information or the protocol type indicationinformation. The IAB node 1 determines the UE and the bearer to whichthe data packet belongs according to the UE identifier and beareridentifier information carried in the adaptor layer header of thereceived data packet; or the IAB node 1 determines the UE and the bearerto which the data packet belongs according to the GTP tunnel informationcarried in the adaptor layer header of the received data packet andtransmits the UE data packet to the UE through the corresponding QoSflow/RLC channel/bearer of the corresponding UE.

Embodiment Two: GTP-U+Adaptor Layer

This embodiment method is a second method for routing according toadaptor layer information. The difference from the embodiment one liesin that: a GTP-U protocol layer is provided above an adaptor layer, thatis, an F1 GTP tunnel needs to be established between an IAB node 1 andan IAB donor, and the tunnel is used for transmitting a data packet of aUE. A protocol stack between the UE and a UPF is shown in FIG. 4 andFIG. 5. In FIG. 4 and FIG. 5, the adaptor layer is located above an RLClayer of an IAB node and the IAB donor. It should be noted that, inother embodiments, the adaptor layer may also be located between the RLClayer and a media access control (MAC) layer, or an adaptor layerfunction is located in the RLC layer or the MAC layer.

A difference from the method in the embodiment one includes that F1-Udata between the IAB node1 and the IAB donor is carried by an F1 GTP-Utunnel. The F1 GTP-U tunnel one-to-one corresponds to a bearer of theUE, which may be used for identifying the UE and the bearer to which thedata packet belongs. Therefore, an adaptor layer header does not need toinclude a UE identifier and a bearer identifier. In addition, the methodin the embodiment one is also applicable to embodiment two.

Two modes of protocol stacks of a donor CU and a donor DU are provided,as shown in FIG. 4 and FIG. 5 respectively. In addition, a protocolstack architecture method shown in FIG. 4B is also used. In the methodshown in FIG. 4, after the data reaches the IAB donor, the donor DUtransmits data of the UE's F1 GTP-U tunnel (a F1-U tunnel, i.e., a GTPtunnel of an F1 interface) to the donor CU through another F1-U tunnel.Two F1-U tunnels are in one-to-one correspondence to each other. Thenthe Donor CU may identify the UE and the bearer to which the data packetbelongs through TEID information in the F1-U tunnel, and then maydeliver the data packet to a corresponding PDCP entity.

An uplink data forwarding process using this embodiment method is asfollows. It should be noted that steps described below may be used inany combination.

In step one, after the UE's data packet is encapsulated and processed bya corresponding protocol layer (such as an SDAP/PDCP/RLC/MAC/PHY), theUE's data packet is transmitted to the IAB node 1 through an airinterface.

In step two, after receiving the UE's data and performing thecorresponding PHY/MAC/RLC analysis, the IAB node 1 determines a targetnode and a next-hop node of the data packet according to the obtainedrouting information, or determines a routing path.

For contents included in routing related information, reference may bemade to description in Example one. The IAB node 1 may obtain therouting related information from an access side network element throughRRC signaling, F1 signaling, X2 signaling, or Xn signaling; where theaccess side network element is one of: a gNB-CU, the IAB donor, a gNB,and an eNB; or the IAB node 1 may obtain the routing related informationfrom a core network element through S1 signaling or NG signaling; or theIAB node 1 obtains the routing related information from an applicationserver;

The routing related information may be configured at a granularity ofthe UE; or the routing related information may be configured for eachUE's bearer, that is, the corresponding routing related information isconfigured for each UE's bearer; or the routing related information mayalso be configured for each UE's bearer type, that is, the correspondingrouting information is configured for each UE's bearer type. The IABnode1 may determine the target node and/or the next-hop node of the datapacket according to an RLC channel or a bearer identifier or a bearertype and/or the routing related information to which the data packetreceived from the UE belongs. Optionally, for a split bearer of the UE,the bearer's data may be forwarded to two or more different targetnodes.

In step three, the IAB node 1 maps the parsed PDCP PDU to thecorresponding F1 GTP tunnel according to a mapping relationship betweenthe configured radio bearer and the F1 GTP tunnel. After performing theGTP-U processing and encapsulation, the IAB node 1 performs the adaptorlayer processing and encapsulation on the data packet, i.e., adds theadaptor layer header to the UE data packet. The adaptor layer headerincludes at least one piece of the following information: a target nodeidentifier, and routing path information. Optionally, the IAB node 1 mayobtain UE bearer information and corresponding GTP tunnel informationfrom the CU in a UE context setup request of the F1 signaling.

In step four, the IAB node 1 determines that the next-hop node is an IABnode 2, and then the data packet encapsulated by the adaptor layer istransmitted to the IAB node 2 through the RLC channel or the radiobearer between the IAB node 1 and the IAB node 2.

The IAB node 1 needs to map the UE's data packet to the RLC channel orthe radio bearer of the IAB node 1 and transmits the data packet to theIAB node 2 (Ibid). Specifically, the IAB node 1 may map the UE's datapacket to the RLC channel or the radio bearer of the IAB node 1 based onmethods described below.

Method one: the IAB node1 maps the UE's data packet to the correspondingbearer according to a specific mapping rule.

Specifically, the IAB node1 obtains a 5QI or QCI value of a QoS flow orthe bearer to which the UE data packet belongs from the received UE datapacket. Then according to a mapping relationship between the configuredQCI and a differentiated services code point (DSCP), or a mappingrelationship between the 5QI and the DSCP, or a mapping relationshipbetween the QCI and type of service (TOS), or a mapping relationshipbetween the 5QI and the TOS, the corresponding DSCP or a TOS value areobtained. Then the IAB node1 maps the UE data packet to the bearer orthe QoS flow of the corresponding IAB node1 according to the DSCP or theTOS value and the configured packet mapping rules (such as a packetfilter set, or a TFT). Optionally, if the IAB node 1 maps the UE datapacket to the corresponding QoS flow according to the DSCP or TOS valueand the configured packet mapping rules, then the IAB node 1 maps theQoS flow to the radio bearer, and transmits the UE data packet to theIAB node 2 through the corresponding radio bearer.

Method two: the IAB node 1 obtains a 5QI or QCI value of a QoS flow orthe bearer to which the UE data packet belongs from the received UE datapacket, and then maps the data packet to the bearer or the QoS flowcorresponding to the QCI or 5QI value in the configured QoS rules or theTFT. Optionally, if the UE data packet is mapped to the correspondingQoS flow, the IAB node 1 then maps the QoS flow to the radio bearer, andtransmits the UE data packet to the IAB node 2 through the correspondingradio bearer.

Method three: the IAB node 1 performs the corresponding mappingaccording to a mapping relationship between a logic channel of the IABnode 1 and a logical channel of the configured UE (such as a mappingrelationship between logical channel IDs (LCIDs)) or a mappingrelationship between a radio bearer of the IAB node 1 and a radio bearerof the UE (such as a mapping relationship between radio bearer IDs(RBIDs)). The mapping relationship may be a predefined or one-to-onecorrespondence relationship, or the mapping relationship may beconfigured in one of the following manners: the F1 signaling, the RRCsignaling, the X2 signaling, the Xn signaling, the S1 signaling and theNG signaling.

In step five, after receiving the data packet, the IAB node 2 parses thecorresponding protocol layer (such as a PHY/MAC/RLC/adaptor layer),obtains information in the adaptor layer header, such as the target nodeidentifier, the UE identifier to which the data packet belongs, thebearer identifier to which the data packet belongs, a channel identifierto which the data packet belongs and the routing path information.Alternatively, the IAB node 2 only reads the information in the adaptorlayer header, but does not remove the adaptor layer header. In thiscase, the IAB node 2 does not encapsulate the adaptor layer header. TheIAB node 2 determines the target node according to the information inthe adaptor layer header, and determines the next-hop node as the targetnode (donor DU) by checking the routing table.

Optionally, the IAB node 2 adds the adaptor layer header to the datapacket, the adaptor layer header includes at least one of: the targetnode identifier, the channel identifier to which the data packet belongsand the routing path information. The IAB node 2 transmits theencapsulated data packet to the IAB donor through the RLC channel or theradio bearer between the IAB node 2 and the IAB donor. The mappingbetween the RLC channel/radio bearer of the IAB node 1 and the RLCchannel/radio bearer of the IAB node 2 may refer to the method in thestep four. The IAB node 2 performs the corresponding RLC/MAC/PHYprocessing on the data packet and transmits the data packet to an IABdonor DU (the DU in the IAB donor or the DU connected to the CU in theIAB donor).

In step six, the IAB donor DU parses the PHY/MAC/RLC/adaptor layer andthe GTP-U on the data packet to obtain at least one piece of thefollowing information: the target node identifier, the UE identifier towhich the data packet belongs, the bearer identifier to which the datapacket belongs, the channel identifier to which the data packet belongs,the routing path information, the routing path information, and GTP-Utunnel information.

In an architecture of FIG. 4, there is no adaptor layer on the CU. TheIAB donor DU transmits the data packet to the IAB donor CU through anF1-U GTP tunnel between the IAB donor DU and the IAB donor CU. The IABdonor DU maps each radio bearer of each UE to the F1-U GTP tunnel. Afterreceiving the data packet, the donor DU determines a GTP tunnel to whichthe data packet belongs, and then the donor DU maps the GTP tunnelbetween the IAB node 1 and the donor DU to the corresponding GTP tunnelbetween the donor DU and the donor CU and transmits the GTP tunnel tothe donor CU, and the mapping relationship may be configured by thedonor CU.

In an architecture of FIG. 5, the IAB donor DU encapsulates the adaptorlayer header for the data packet, the adaptor layer header includes atleast one of: the target node identifier and the routing pathinformation. Alternatively, the IAB donor DU only reads the informationin the adaptor layer header, but does not remove the adaptor layerheader. In this case, the IAB donor DU does not encapsulate the adaptorlayer header. The IAB donor DU transmits the data to the IAB donor CUthrough the F1-U GTP tunnel.

In step seven, in the architecture of FIG. 4, the donor CU identifiesthe UE and the bearer to which the data packet belongs according totunnel information in a GTP-U header, and delivers the UE data packet tothe PDCP entity for the corresponding bearer of the corresponding UE toperform subsequent parsing.

In the architecture of FIG. 5, the donor CU obtains at least one of thefollowing information by parsing the adaptor layer: the target nodeidentifier and the routing path information. After the donor CU obtainsthe GTP-U tunnel to which the data packet belongs and the correspondingUE and the bearer to which the data packet belongs by parsing the GTP-Uprotocol layer, the donor CU delivers the UE data packet to the PDCPentity for the corresponding bearer of the corresponding UE to performthe subsequent parsing.

Then the SDAP layer of the donor CU finds an NG GTP-U tunnelcorresponding to a PDU session according to a RB ID to which the datapacket belongs and a flow ID of the UE in the SDAP packet header, andtransmits the UE data to the UPF through the NG GTP tunnel.

A downlink data forwarding process using this embodiment method is asfollows. It should be noted that steps described below may be used inany combination.

A difference from the embodiment one is that the F1-U data between theIAB node1 and the IAB donor is carried by the F1 GTP-U tunnel. The F1GTP-U tunnel one-to-one corresponds to a bearer of the UE, which may beused for identifying the UE and the bearer to which the data packetbelongs. Therefore, an adaptor layer header does not need to include aUE identifier and a bearer identifier.

In step one, after receiving the UE data from the UPF, the CU in the IABdonor determines the QoS flow of the PDU session corresponding to the UEdata packet according to the QFI in the data packet header, and thenmaps the QoS flow to the corresponding radio bearer. The IAB donor needsto determine the target node of the data packet. In this case, thetarget node of the data packet is the serving IAB node of the UE (i.e.,the IAB node 1). The IAB donor may determine the target node (theserving IAB node) of the data packet according to or serving IAB nodeinformation corresponding to the radio bearer, or serving IAB nodeinformation corresponding to the bearer type, or serving IAB nodeinformation in a UE context. The CU in the IAB donor transmits the UEdata packet to the DU in the IAB donor or the DU connected to the CU inthe IAB donor.

If the architecture shown in FIG. 4 is adopted, there is no adaptorlayer on the CU, and the donor CU transmits the UE data to the donor DUthrough an F1 GTP bearer.

If the architecture of FIG. 5 is adopted, that is, there is the adaptorlayer on the CU, the CU in the IAB donor maps the PDCP PDU to thecorresponding F1-U tunnel, and adds the adaptor layer header andtransmits the adaptor layer header to the donor DU after the GTP-Uprocessing and encapsulation. The adaptor layer header includes at leastone of: the target node identifier, the routing path information, andQoS related information. The QoS related information is the QCI or 5QIvalue of the UE data packet.

In step two, if the architecture shown in FIG. 4 is adopted, the donorDU acquires GTP tunnel information between the donor DU and the donor CUand GTP tunnel information between the corresponding IAB node 1 and thedonor CU from the CU. After receiving the UE data packet from the CU,the donor DU determines a GTP tunnel between the IAB node 1 and thedonor CU corresponding to a GTP tunnel between the donor CU and thedonor DU to which the data packet belongs, and maps the tunnel (the GTPtunnel between the IAB node 1 and the donor CU) to the corresponding GTPtunnel between the donor DU and the IAB node 1 and performs thecorresponding GTP-U encapsulation. And then the adaptor layer processingand encapsulation are performed. The added adaptor layer header includesat least one of: the target node identifier, the routing pathinformation and the QoS related information. The QoS related informationis the QCI or 5QI value of the UE data packet. Optionally, the DU mapsthe data packet to the QoS flow/bearer of the IAB node 2 with thecorresponding QCI or 5QI value according to the DSCP or TOS informationin the IP packet header and transmits the data packet to the IAB node 2.

If the architecture shown in FIG. 5 is adopted, after receiving the UEdata packet from the CU, the donor DU obtains at least one of thefollowing information by parsing the adaptor layer: the target nodeidentifier, the routing path information, and the QoS relatedinformation. The donor DU determines a next-hop routing node (the IABnode 2) according to the above information and the routing table.Optionally, the donor DU performs the adaptor layer protocolencapsulation.

The adaptor layer header includes at least one of: the target nodeidentifier, the routing path information and the QoS relatedinformation. Optionally, the donor DU determines QoS information of thereceived data packet according to adaptor layer header information ofthe received data packet, or maps the data packet to the QoS flow/bearerof the IAB node 1 with the corresponding QCI or 5QI value according tothe DSCP or TOS information in the IP header, and transmits the datapacket to the IAB node 2.

In step three, after receiving the data packet, the IAB node 2 obtainsat least one of the following information by parsing the adaptor layer:the target node identifier, the routing path information, and the QoSrelated information. The IAB node 2 determines a next-hop routing node(the IAB node 1) according to the above information and the routingtable. Optionally, the IAB node 2 performs the adaptor layer protocolencapsulation. The adaptor layer header includes at least one of: thetarget node identifier, the routing path information and the QoS relatedinformation. Optionally, the IAB node 2 determines QoS information (theQCI or 5QI value) according to the bearer or QoS flow to which thereceived data packet belongs, or determines the QoS informationaccording to adaptor layer header information of the received datapacket, and then maps the data packet on the QoS flow/bearer/logicchannel of the IAB node 1 with the corresponding QCI or 5QI value andtransmits the data packet to the IAB node 1.

In step four, after receiving the data packet, the IAB node 1 obtains atleast one of the following information by parsing the adaptor layer: thetarget node identifier, the routing path information, and the QoSrelated information. Then the IAB node 1 may obtain the UE and bearer towhich the data packet belongs by parsing the GTP-U protocol layer, andthen transmits the UE data packet to the UE through the correspondingQoS flow/RLC channel/bearer corresponding to the UE.

Embodiment Three: PDU Session+Adaptor

This embodiment method is a method three for routing according toadaptor layer information. A protocol stack between a UE and a UPF isshown in FIG. 6. In FIG. 6, the adaptor layer is located above an RLClayer of an IAB node and an IAB donor. It should be noted that theadaptor layer may also be located between the RLC layer and a mediaaccess control (MAC) layer, or an adaptor layer function is located inthe RLC layer or the MAC layer.

The difference from methods in the embodiments one and two is that F1-Udata between an IAB node1 and the IAB donor is carried by a PDU sessionof the IAB node 1, and an adaptor layer header does not need to includea UE identifier and a bearer identifier. In addition, the method in theembodiment two is also applicable to embodiment three.

After receiving uplink data of the UE, the IAB node 1 corresponds a PDCPPDU to a corresponding F1-U GTP tunnel after parsing out the PDCP PDU.And then the IAB node takes an F1-U packet of the encapsulated UE asdata of the IAB node itself that serves as the UE, and the IAB nodetransmits the data to the UPF of the IAB node itself through the PDUsession of the IAB node itself, and the data may need to be forwarded byan intermediate IAB node during the transmission. The IAB node 1 needsto map the UE's F1-U GTP bearer to a QoS flow or bearer of the IAB node1. Optionally, the IAB node 1 may map the data packet to thecorresponding QoS flow or bearer according to QoS information (QCI or5QI) of the bearer to which the data packet received from the UE belongsand a packet filter set (including an IP packet filter set and anEthernet packet filter set) in QoS rules. Alternatively, the IAB node 1may determine the corresponding DSCP/TOS value according to the QoSinformation of the bearer to which the data packet received from the UEbelongs and a mapping relationship between the QoS information and aDSCP/TOS, and then map the UE data packet to the corresponding QoS flowor bearer according to the DSCP/TOS. If the IAB node1 maps the UE datapacket to the QoS flow, the IAB node1 also needs to map the QoS flow toa DRB of the IAB node1. After the corresponding PDCP processing, the IABnode1 adds the adaptor layer header, and the added adaptor layer headerincludes target node identifier information and/or routing pathinformation.

One or more intermediate IAB nodes route the data packet to the donor DUaccording to routing information in the adaptor layer. A CU function ofthe UE in the IAB donor may identify the UE and the bearer to which thedata packet belongs according to GTP-U header information (such as an F1GTP TEID), and deliver the data packet to a PDCP entity for thecorresponding bearer.

It will be understood by those of ordinary skill in the art thatfunctional modules/units in all or part of the steps of the method, thesystem and the apparatus disclosed above may be implemented as software,firmware, hardware and appropriate combinations thereof. In the hardwareimplementation, the division of the functional modules/units mentionedin the above description may not correspond to the division of physicalcomponents. For example, one physical component may have severalfunctions, or one function or step may be implemented jointly by severalphysical components. Some or all components are implemented as softwareexecuted by processors such as central processing units, digital signalprocessors or microcontrollers, hardware, or integrated circuits such asapplication specific integrated circuits. Such software may bedistributed on a computer-readable medium. The computer-readable mediummay include a computer storage medium (or a non-transitory medium) and acommunication medium (or a transitory medium). As is known to those ofordinary skill in the art, the term “computer storage medium” includesvolatile and nonvolatile, removable and non-removable media implementedin any method or technology for storing information (such ascomputer-readable instructions, data structures, program modules orother data). The computer-storage medium include, but is not limited to,a random access memory (RAM), a read-only memory (ROM), an electricallyerasable programmable read-only memory (EEPROM), a flash memory, orother memory technologies, a compact disc read-only memory (CD-ROM), adigital versatile disc (DVD) or other optical disc storage, a magneticcassette, a magnetic tape, disk storage or other magnetic storageapparatus, or any other medium used to store the desired information andaccessible by a computer. Additionally, as is known to those of ordinaryskill in the art, the communication medium generally includescomputer-readable instructions, data structures, program modules orother data in modulated data signals such as carriers or othertransmission mechanisms, and may include any information deliverymedium.

1. A method for performing relay forwarding on integrated access andbackhaul (IAB) links, comprising: receiving, by a first IAB node, a datapacket; and transmitting, by the first IAB node, the data packet to anIAB donor; wherein the receiving, by a first IAB node, a data packetcomprises: receiving, by the first IAB node, the data packet from a userequipment (UE); or receiving, by the first IAB node, the data packetfrom an application layer of the first IAB node itself; or receiving, bythe first IAB node, the data packet from another IAB node; the datapacket is user-plane data or control-plane signaling; the transmitting,by the first IAB node, the data packet to an IAB donor comprises:obtaining, by the first IAB node, routing related information, andtransmitting the data packet to the IAB donor according to the routingrelated information; the routing related information comprises at leastone of: a source node identifier; a source node address; a target nodeidentifier; a target node address; routing path information; a bearertype; a bearer identifier; a master base station or a master nodeidentifier; a master base station or a master node address; a secondarybase station or a secondary node identifier; a secondary base station ora secondary node identifier; routing path information about routing to amaster node or to the master base station; routing path informationabout routing to a secondary node or to the secondary base station; anext-hop node ID; a next-hop address; or general packet radio servicetunneling protocol (GTP) tunnel information. 2.-5. (canceled)
 6. Themethod of claim 1, wherein the obtaining, by the first IAB node, routingrelated information comprises at least one of the following manners:obtaining, by the first IAB node, the routing related information froman access side network element through radio resource control (RRC)signaling, F1 signaling, X2 signaling, Xn signaling or other interfaceinformation; obtaining, by the first IAB node, the routing relatedinformation from a core network element through S1 signaling, NGsignaling, or other interface information; obtaining, by the first IABnode, the routing related information from an application server;obtaining, by the first IAB node, the routing related information froman adaptor layer header of the received data packet; or obtaining, bythe first IAB node, the routing related information from an Internetprotocol (IP) layer header of the received data packet.
 7. The method ofclaim 1, wherein a configuration mode of the routing related informationcomprises: configuring the routing related information obtained by thefirst IAB node at a granularity of a UE; configuring the routing relatedinformation at a granularity of a UE's bearer, wherein the first IABnode obtains a bearer identifier and routing related informationcorresponding to the bearer identifier; or configuring the routingrelated information at a granularity of a UE's bearer type, wherein thefirst IAB node obtains a bearer type and routing related informationcorresponding to the bearer type.
 8. The method of claim 1, wherein thetransmitting, by the first IAB node, the data packet to an IAB donorcomprises: adding, by the first IAB node, an adaptor layer header to thedata packet, wherein the adaptor layer header comprises at least one of:a source node identifier, a target node identifier, a UE identifier towhich the data packet belongs, a bearer identifier to which the datapacket belongs, a channel identifier to which the data packet belongs,routing path information, Quality of Service (QoS) related information,general packet radio service tunneling protocol (GTP) tunnelinformation, control plane indication information, user plane indicationinformation, or protocol type indication information.
 9. The method ofclaim 8, wherein the adding an adaptor layer header is performed by anadaptor layer located above a radio link control (RLC) layer; or anadaptor layer located between the RLC layer and a media access control(MAC) layer; or an adaptor layer functional entity located at the RLClayer; or an adaptor layer functional entity located at the MAC layer.10. The method of claim 1, wherein the transmitting, by the first IABnode, the data packet to an IAB donor comprises: transmitting the datapacket to a next-hop node; wherein a mode of transmitting the datapacket to the next-hop node comprises one of: mapping, by the first IABnode according to a mapping rule and at least one of a bearer to whichthe data packet belongs or Quality of Service (QoS) related informationof a QoS flow, the data packet to a corresponding radio bearer totransmit to the next-hop node; mapping, by the first IAB node accordingto the mapping rule and based on one of a logical channel or radiobearer of a UE to which the data packet belongs, or a logical channel orradio bearer of a previous-hop IAB node related to the data packet, thedata packet to a radio bearer or logical channel of the first IAB nodeto transmit to the next-hop node and; wherein the mapping rule comprisesat least one of: a packet mapping rule, a QoS rule, a mapping rulebetween the QoS related information and differentiated services codepoint (DSCP), and a mapping rule between the QoS related information andtype of service (TOS).
 11. The method of claim 1, wherein thetransmitting, by the first IAB node, the data packet to an IAB donorcomprises: mapping, by the first IAB node according to a radio bearer towhich the data packet belongs and a mapping relationship between theradio bearer and a general packet radio service tunneling protocol (GTP)tunnel of an F1 interface, the data packet to the GTP tunnel of the F1interface corresponding to the radio bearer to which the data packetbelongs; adding, by the first IAB node, an adaptor layer header to thedata packet, wherein the adaptor layer header comprises at least one of:a source node identifier, a target node identifier, a user equipment(UE) identifier to which the data packet belongs, routing pathinformation, Quality of Service (QoS) related information, GTP tunnelinformation, control plane indication information, user plane indicationinformation, or protocol type indication information.
 12. (canceled) 13.The method of claim 1, after obtaining, by the first IAB node, therouting related information, further comprising: determining, by thefirst IAB node, a target node and the next-hop node of the data packetaccording to the routing related information, wherein the target nodecomprises one of: an IAB donor, a base station centralized unit (gNB-CU)in the IAB donor, a base station distribution unit (gNB-DU) in the IABdonor, and a gNB-DU connected to the gNB-CU in the IAB donor, a userplane function (UPF), an access and mobility management module (AMF), abase station and an IAB node; and the next-hop node is the IAB donor orthe IAB node; or determining, by the first IAB node, a routing pathaccording to the routing related information.
 14. The method of claim 1,wherein the obtaining, by the first IAB node, routing relatedinformation comprises: obtaining, by the first IAB node, the routingrelated information from an adaptor layer header of the received datapacket; and after obtaining, by the first IAB node, the routing relatedinformation, the method further comprises at least one of: searching, bythe first IAB node according to the routing related information, arouting table to determine the next-hop node, wherein the next-hop nodeis the IAB donor or the IAB node; or adding an adaptor layer header;wherein the target node is the IAB donor, or the gNB-CU in the IABdonor, or the gNB-DU in the IAB donor, or the gNB-DU connected to thegNB-CU in the IAB donor, or the UPF, or the AMF, or the base station, orthe IAB node. 15-18. (canceled)
 19. A method for performing relayforwarding on integrated access and backhaul (IAB) links, comprising:receiving, by an IAB donor, a data packet from a core network element oran application layer; and transmitting, by the IAB donor, the datapacket to an IAB node; receiving, by the IAB node, the data packet fromthe IAB donor; and transmitting, by the IAB node, the data packet to auser equipment (UE).
 20. The method of claim 19, wherein thetransmitting, by the IAB donor, the data packet to an IAB nodecomprises: adding, by the IAB donor, an adaptor layer header to the datapacket after the IAB donor parses the data packet in a correspondingprotocol layer, wherein the adaptor layer header carries at least oneof: a source node identifier, a target node identifier, a UE identifierto which the data packet belongs, and a bearer identifier to which thedata packet belongs, a channel identifier to which the data packetbelongs, routing path information, Quality of Service (QoS) relatedinformation, general packet radio service tunneling protocol (GTP)tunnel information, control plane indication information, user planeindication information or protocol type indication information.
 21. Themethod of claim 20, wherein the adding an adaptor layer header isperformed by: an adaptor layer located above a radio link control (RLC)layer; or an adaptor layer located between the RLC layer and a mediaaccess control (MAC); or an adaptor layer functional entity located atthe RLC layer; or an adaptor layer functional entity located at the MAClayer. 22-24. (canceled)
 25. The method of claim 19, whereintransmitting, by the IAB node, the data packet to the UE comprises:acquiring, by the IAB node, information from an adaptor layer header,determining a next-hop node according to the information, andtransmitting the data packet to the next-hop node, wherein theinformation comprises at least one of: a source node identifier, atarget node identifier, a UE identifier to which the data packetbelongs, and a bearer identifier to which the data packet belongs, achannel identifier to which the data packet belongs, routing pathinformation, Quality of Service (QoS) related information, generalpacket radio service tunneling protocol (GTP) tunnel information,control plane indication information, user plane indication informationor protocol type indication information.
 26. The method of claim 19,wherein transmitting, by the IAB node, the data packet to the UEcomprises: after adding an adaptor layer header to the data packet,transmitting, by the IAB node, the data packet to the next-hop node,wherein information in the adaptor layer header comprises at least oneof: a source node identifier, a target node identifier, a UE identifierto which the data packet belongs, and a bearer identifier to which thedata packet belongs, a channel identifier to which the data packetbelongs, routing path information, Quality of Service (QoS) relatedinformation, general packet radio service tunneling protocol (GTP)tunnel information, control plane indication information, user planeindication information or protocol type indication information. 27.-29.(canceled)
 30. An information acquisition method, comprising: acquiring,by an integrated access and backhaul (IAB) links donor distribution unit(DU), mapping related information; wherein the mapping relatedinformation comprises at least one of: a mapping relationship betweenuser equipment (UE) bearer information and general packet radio servicetunneling protocol (GTP) tunnel information of an F1 interface; amapping relationship between the GTP tunnel information of the F1interface, a target node identifier and UE bearer information; a mappingrelationship between the GTP tunnel information of the F1 interface andthe target node identifier; or a mapping relationship between the GTPtunnel information of the F1 interface; wherein the UE bearerinformation comprises at least one of: a UE identifier or a beareridentifier; wherein the GTP tunnel information of the F1 interfacecomprises at least one of: an address or tunnel endpoint identifier(TEID) information; wherein the IAB donor DU is one of: the IAB node, aDU node in an IAB donor, and a DU node wiredly connected to a CU in theIAB donor.
 31. The method of claim 30, wherein the acquiring, by anintegrated access and backhaul (IAB) links donor distribution unit (DU),mapping related information comprises at least one of: obtaining, by theIAB donor DU, the mapping related information from an access sidenetwork element through radio resource control (RRC) signaling, F1signaling, X2 signaling, Xn signaling or other interface information;obtaining, by the IAB donor DU, the mapping related information from acore network element through S1 signaling, NG signaling, or otherinterface information; or obtaining, by the IAB donor DU, the mappingrelated information from an application server.
 32. An integrated accessand backhaul (IAB) links node in an IAB donor, comprising a memory, aprocessor, and a computer program stored in the memory and executable onthe processor, wherein when executing the computer program, theprocessor implements the method of claim
 1. 33. An integrated access andbackhaul (IAB) links donor node in IAB, comprising a memory, aprocessor, and a computer program stored in the memory and executable onthe processor, wherein when executing the computer program, theprocessor implements the method of claim
 1. 34. A non-transitorycomputer-readable storage medium for storing a computer program which,when executed by a processor, implement the method of claim 1.